Fix "NtCreateFile(\Device\VBoxDrvStub) Failed" Error in VirtualBox | VERR_OPEN_FAILED (-101) Fix [2025]
Are you getting the "NtCreateFile(\Device\VBoxDrvStub) failed" error when trying to start a virtual machine in Oracle VirtualBox? This video provides a complete step-by-step guide to help you fix this common VirtualBox supR3HardenedWinReSpawn error and resolve the VERR_OPEN_FAILED (-101) issue — without reinstalling VirtualBox!
✅ What You’ll Learn:
Understand the root cause of the VBoxDrvStub error
How to fix STATUS_OBJECT_NAME_NOT_FOUND (0xc0000034)
Use SC command-line tools to restart required VirtualBox services
Get your VM up and running again quickly
📌 Full Error Message:
VirtualBox - Error In supR3HardenedWinReSpawn
NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034
STATUS_OBJECT_NAME_NOT_FOUND (0 retries) (rc=-101)
Make sure the kernel module has been loaded successfully.
Where: supR3HardenedWinReSpawn What: 3 VERR_OPEN_FAILED (-101) – File/Device open failed.
Driver is probably stuck stopping/starting. Try 'sc.exe query vboxsup' to get more information about its state.
Rebooting may actually help.
📌 Commands Used in This Video:
sc start vboxsup
sc start vboxdrv
🛠 This tutorial works for:
VirtualBox on Windows 10 / 11
After system reboot or Windows update
Fixing VirtualBox kernel module issues
Driver or permission-related startup failures
🔍 Keywords:
VirtualBox error fix, NtCreateFile VBoxDrvStub failed, VirtualBox STATUS_OBJECT_NAME_NOT_FOUND, VERR_OPEN_FAILED VirtualBox solution, supR3HardenedWinReSpawn error, VirtualBox won't start VM, VBoxDrvStub missing, fix VirtualBox driver error, VirtualBox kernel module not loaded, sc start vboxdrv command, VirtualBox VM fails to launch, Windows VirtualBox troubleshooting, VBoxDrvStub device error, 0xc0000034 VirtualBox fix, how to fix VirtualBox after reboot, VirtualBox failed to open session for virtual machine
#️⃣ Hashtags:
#VirtualBoxFix #VERR_OPEN_FAILED #NtCreateFileError
